CVE-2026-33473
Vikunja has TOTP Reuse During Validity Window
Description
Vikunja is an open-source self-hosted task management platform. Starting in version 0.13 and prior to version 2.2.1, any user that has enabled 2FA can have their TOTP reused during the standard 30 second validity window. Version 2.2.1 patches the issue.
INFO
Published Date :
March 24, 2026, 4:16 p.m.
Last Modified :
March 27, 2026, 4:53 p.m.
Remotely Exploit :
Yes !
Source :
[email protected]
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 3.1 | MEDIUM | [email protected] |
Solution
- Update Vikunja to version 2.2.1 or later.
- Ensure 2FA is enabled for all users.
- Monitor for any authentication anomalies.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-33473.
| URL | Resource |
|---|---|
| https://github.com/go-vikunja/vikunja/security/advisories/GHSA-p747-qc5p-773r | Exploit Vendor Advisory |
| https://vikunja.io/changelog/vikunja-v2.2.0-was-released | Release Notes |
| https://vikunja.io/changelog/vikunja-v2.2.2-was-released | Release Notes |
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-33473 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-33473
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-33473 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-33473 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
Initial Analysis by [email protected]
Mar. 27, 2026
Action Type Old Value New Value Added CWE NVD-CWE-noinfo Added CPE Configuration OR *cpe:2.3:a:vikunja:vikunja:*:*:*:*:*:*:*:* versions from (including) 0.13 up to (excluding) 2.2.1 Added Reference Type GitHub, Inc.: https://github.com/go-vikunja/vikunja/security/advisories/GHSA-p747-qc5p-773r Types: Exploit, Vendor Advisory Added Reference Type GitHub, Inc.: https://vikunja.io/changelog/vikunja-v2.2.0-was-released Types: Release Notes Added Reference Type GitHub, Inc.: https://vikunja.io/changelog/vikunja-v2.2.2-was-released Types: Release Notes -
New CVE Received by [email protected]
Mar. 24, 2026
Action Type Old Value New Value Added Description Vikunja is an open-source self-hosted task management platform. Starting in version 0.13 and prior to version 2.2.1, any user that has enabled 2FA can have their TOTP reused during the standard 30 second validity window. Version 2.2.1 patches the issue. Added CVSS V3.1 AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N Added CWE CWE-287 Added Reference https://github.com/go-vikunja/vikunja/security/advisories/GHSA-p747-qc5p-773r Added Reference https://vikunja.io/changelog/vikunja-v2.2.0-was-released Added Reference https://vikunja.io/changelog/vikunja-v2.2.2-was-released